home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The X-Philes (2nd Revision)
/
The X-Philes Number 1 (1995).iso
/
xphiles
/
hp48_2
/
chasm01.sha
/
README
< prev
next >
Wrap
Text File
|
1995-03-23
|
2KB
|
60 lines
/*
* README - chasm README file
*
* @(#)README 1.1 91/04/10
*
* Copyright (c) 1991 Steve Scherf
*
* Author: Steve Scherf
* Date: Wed Apr 10 22:53:11 PDT 1991
*
*/
Chasm v0.1
Since you're reading this, you've most likely unshar-ed the chasm package.
The unpacked files should include:
chasm.c
chasm.doc
chasm.h
grammar.y
lex.c
link.c
Makefile
README
sample.ch
Chasm is written for System V Unix, but should run under BSD and other
operating systems with little or no modification. To compile, merely type
"make". The result should be the successful compilation of a binary called
"chasm". This program was written mostly as an exercise in learning yacc
and general assembler construction, and as a result is probably a little
over-complex. There are many features that are not really necessary, but
are useful and might come in handy. Chasm really does make it easy to write
Chip 48 programs!
At this point I have extensively tested chasm to make sure it generates the
opcodes laid out in the original Chip 48 v2.25 document. Each instruction
does indeed produce the proper opcode. However, I have only written a few
programs with it and have not actually tested every instruction in the context
of a program. Therefore, it is possible that some instructions may not work
properly if the documentation is erroneous; nevertheless, I believe that chasm
is fairly bug-free.
Chasm is simple to use. Simply type "chasm filename" where "filename" is
a file containing chasm assembly instructions. If chasm successfully
assembles the file, the result should be a file called "c.out" which contains
an executable Chip 48 binary. This file can be downloaded to the HP 48
via kermit (make sure the mode is set to binary).
Included is a sample chasm file called sample.ch. Try assembling and
running it!
If you have any questions, comments or bugs to report, don't hesitate to send
email. I can't promise that I will respond very quickly since I am often
very busy, but I will try.
Steve Scherf
steve@Altos.COM